home *** CD-ROM | disk | FTP | other *** search
- 1 MercuryX Scheduling Module
- 3 MercuryX
- 70 Activating module '%s'
- 71 [Idle]
- 100 MercuryX Task Scheduler
- 200 Sunday
- 201 Monday
- 202 Tuesday
- 203 Wednesday
- 204 Thursday
- 205 Friday
- 206 Saturday
- 250 Running '%s'...
- 251 Waiting for process to terminate...
- 252 Waiting for timeout to elapse...
- 253 Waiting for processes to complete...
- 299 Starting server and client tasks...
- 300 Active, on peak cycle
- 301 Active, on off-peak cycle
- 302 Shutting down server and client tasks...
- 303 System is offline
- 304 [Off]
- 400 # ETRN Configuration File for Mercury/32\n
- 401 #\n
- 402 # Mercury can 'kick-start' remote queues by sending SMTP ETRN\n
- 403 # commands to the servers that host those queues. This file\n
- 404 # tells Mercury which hosts it needs to contact, and the name of\n
- 405 # the queues it should trigger on those hosts.\n
- 406 #\n
- 407 # Enter the name of a host that Mercury should contact hard\n
- 408 # against the left-hand margin of this file. Then on subsequent\n
- 409 # lines, enter the names of the domains that should be triggered,\n
- 410 # indented by at least one space. Repeat this process for all the\n
- 411 # hosts Mercury should contact. Blank lines, and lines starting\n
- 412 # with '#' are treated as comments and ignored.\n
- 413 # \n
- 414 # Example: you want Mercury to contact the host 'mail.caramba.org'\n
- 415 # and ask it to trigger the mail queues for 'arriba.com' and\n
- 416 # 'ayayay.com': you would create the following entry:\n
- 417 #\n
- 418 # mail.caramba.org\n
- 419 # arriba.com\n
- 420 # ayayay.com\n
- 421 \n
-